Getting Started with Member Attributes

Overview

Member Attributes represent the data fields in your Loyalty database. They store information about each Member in their Member Profile and are used throughout the platform, such as to personalize content or to define selection criteria for Segments.

The platform includes a wide range of default System Attributes applicable to many client loyalty programs. You can also create custom Member Attributes to capture information unique to your brand and business needs.

Note: The default System Attributes can be identified by the label "System" within the Settings column on the Member Attributes screen.

Loyalty supports a variety of Attribute configuration options, such as different data types, the use of pre-defined values, or the use of a default value. You can make Attributes read-only, required, or static. For advanced use cases, you can create Calculated Attributes that are populated based on the output of an expression.

From the Member Attributes screen, you can view information about all the Attributes defined in your Loyalty database. You can also create new Attributes. To access the Member Attributes screen, select Program from the top navigation bar, then select Member Attributes from the side navigation menu.

For more information on the search options available on the Member Attributes screen, see Search for a Member Attribute.

Member Attribute Categories

To make Member Attributes easier to find and manage, you can group them into Member Attribute Categories based on their purpose or content. These Categories appear on the Member Profile screen, helping Customer Service Representatives (CSRs) quickly locate relevant information.

See Getting Started with Member Attribute Categories for more information.

Specialized Member Attributes

The Loyalty platform utilizes dedicated Member Attributes for the following specialized purposes:

  • Marigold Artificial Intelligence: Member Profiles can capture and manage Marigold AI scores related to “likelihood to purchase," the optimal Offer value needed to incentivize the next purchase, and reducing over-discounting. In future releases, Marigold’s AI capability will help clients optimize Offer targeting to improve Member engagement, and to improve program margins.

  • Member Identifiers: The following system Attributes can be used throughout the platform to uniquely identify a Member:

    • Email: The Member's email address.

    • Member ID: A unique string that identifies the Member within the platform.

    • Integration ID: A unique string that identifies the Member in a third-party system (e.g., an eCommerce ID).

    • Mobile Phone: The Member's mobile phone number.

    • Card ID: A unique string on a physical card that identifies the Member.

  • Subscription: This special type of Attribute is used to manage a Member’s eligibility to be contacted in a marketing campaign.

Populate a Member Attribute

The Loyalty platform supports a wide range of options for populating or updating the value stored in a Member Attribute. Some of these options include:

  • Manual: Via the Member Profile screen, a CSR can manually update or populate a Member Attribute. See Edit Member Attributes for more information.

  • Import: You can import a file into Loyalty to update or populate multiple Member Attributes. The import process allows you to map each column in the import file to the desired Member Attribute. You can also configure additional details, such as only writing new records, or overwriting existing values with the values in the import file. See Imports for more information.

  • API Request: Loyalty clients are able to send API requests with Member Attribute values that will populate or update a Member record. For more information, see the Member API technical documentation.

  • Calculated Attributes: The value in a Calculated Attribute is derived based on an expression. The value can be updated on-demand, or on a scheduled basis. See Create a Calculated Attribute for more information.

  • Triggered Action: Triggered Actions monitor changes to a Member Profile, and automatically execute a specific action if a specific condition is met. The action can be expressed using Groovy, and can be used to derive a value and populate a Member Attribute. See Triggered Actions for more information.

Note: Triggered Actions differ from Calculated Attributes mostly regarding when the value is refreshed. A Triggered Action executes only when its specified triggering incident occurs. In general, you can consider using a Triggered Action in place of a Calculated Attribute if the Attribute value is calculated only once, or if there is no need to recompute the value.

View a Member Attribute Create a Member Attribute Create a Calculated Attribute